projects / xen.git / commit
? search:
summary | shortlog | log | commit | commitdiff | tree
(parent: 20f482d) | patch
Don't treat the failure of ifconfig vifX.Y down as a fatal error. This hasn't
authoremellor@leeni.uk.xensource.com <emellor@leeni.uk.xensource.com>
Wed, 23 Nov 2005 19:16:54 +0000 (19:16 +0000)
committeremellor@leeni.uk.xensource.com <emellor@leeni.uk.xensource.com>
Wed, 23 Nov 2005 19:16:54 +0000 (19:16 +0000)
commit92b5e8126492696a3ec1ad887ce296c798a549f7
tree54e51760e9c5a7efad0888b58a786e35d69b40fdtree | snapshot
parent20f482d49498f2115de3f7c8fb944d2f23056b01commit | diff
Don't treat the failure of ifconfig vifX.Y down as a fatal error.  This hasn't
emerged as a problem in the field, AFAIK, but it seems that distro scripts
could have brought the device down already by this point (Debian stable's
net.agent does ifdown vifX.Y, and it wouldn't surprise me if someone decided
to do ifconfig vifX.Y down if this failed, for example).

Logging but ignoring the failure seems sensible.

Signed-off-by: Ewan Mellor <ewan@xensource.com>
tools/examples/vif-bridge diff | blob | history
Unnamed repository; edit this file 'description' to name the repository.